This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Preventing access to a local replica ~Naomi Deskroterakol 7.Jan.04 11:08 PM a Web browser Notes Client All ReleasesAll Platforms
First, the question here was about certificate expiration, not replication history. Graham's suggestion was to have short expire times (which has it's own benefits and costs.) My question was: why would short certificate expiration help protect a local copy? The only method would be by forcing that local version to be encrypted with that ID (which you can't really do) and then expire the ID, which should prevent the Notes client from doing meaningful work with it.
However, this strategy is defeated by setting the clock back.
As far as your replication history approach goes, you've got the same problem, as Chuck points out. You could make the open script so clever as to *silently* kill the replica of the NSF, but given that the entire approach fails if the user ever writes the NSF to CD, you've got half-a-dozen Notes experts telling you: this is not information protection, and you shouldn't allow yourself or your client to pretend that it is.
Return to top
. . . . . . . . . . . . . . RE: Preventing access to a local re... (~Naomi Deskrote... 7.Jan.04) 
Print this page
